Fix and cleanup security scopes #2129
Conversation
api-clients-generation-pipeline
bot
requested a review
from a team
as a code owner
api-clients-generation-pipeline
bot
force-pushed
the
datadog-api-spec/generated/3373
branch
from
ebeeb82 to
8c8383a
Compare
![datadog-datadog-prod-us1[bot]](https://avatars.githubusercontent.com/u/365230?s=60&v=4){kind=small}
|
|
||
| # auth_names | ||
| auth_names = opts[:debug_auth_names] || [:apiKeyAuth, :appKeyAuth, :AuthZ] | ||
| auth_names = opts[:debug_auth_names] || [:apiKeyAuth, :appKeyAuth] |
There was a problem hiding this comment.
⚪ Code Quality Violation
| auth_names = opts[:debug_auth_names] || [:apiKeyAuth, :appKeyAuth] | |
| auth_names = opts[:debug_auth_names] || %i[apiKeyAuth appKeyAuth] |
Consider using the %i syntax instead (...read more)
The rule "Prefer %i to the literal array syntax" is a guideline that encourages the use of the %i syntax for arrays of symbols. This is a part of the Ruby style guide that aims to promote conciseness and readability.
Symbols are immutable, reusable objects often used in Ruby instead of strings when the value does not need to be changed. When declaring an array of symbols, using the %i syntax can make your code cleaner and easier to read.
To adhere to this rule, instead of declaring an array of symbols using the literal array syntax like [:foo, :bar, :baz], use the %i syntax like %i[foo bar baz]. It's a good practice to consistently use %i for arrays of symbols as it enhances code readability and maintainability.
See DataDog/datadog-api-spec#3373
Test branch datadog-api-spec/test/sherz/fix-security-schemes